Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.036

Text File | 1996-02-12 | 27.7 KB | 763 lines

Frequently Asked Questions (FAQS);faqs.036



  This is only a half-facetious question; there's only room on most
  workstation screens (usually 1024x768 or 1280x1024 pixels in area) for
  a couple of windows with decent-sized fonts.  To help alleviate the
  discomfort of cramped space, try the 'tvtwm' window manager.  (I sound
  like a cough-drop commercial.)

  Tvtwm, a superset of the twm window manager, allows windows to be
  placed on a virtual root window that can be of any size (for example,
  3000 by 3000 pixels).  This virtual root can be navigated via tvtwm's
  'panner', a reduced-size overview of your entire environment.

  Tvtwm can be found on your local comp.sources.x archive or in the
  X11R4 and X11R5 distributions.  Try anonymous FTP to ftp.uu.net
  (137.39.1.9) in /usenet/comp.sources.x.

  For those people that actually like the OpenLook window manager :-),
  a similarly modified version of Olwm can be found in ftp.uu.net
  /usenet/comp.sources.x/volume14/olvwm (and a lot of other places,
  too).

  People running on HP workstations can use the rooms metaphor built
  into the vuewm.  A similar, but less powerful alternative is the vr
  program in the contrib directory at export.lcs.mit.edu.  It,
  however, doesn't support spreading epoch windows around different
  rooms.

*                      === COLORS AND FONTS ===

D-1: How do I interactively select my foreground color?

  First, define a style for each of your desired foreground colors in
  your .emacs file, like so:

    (setq red-style (make-style))
    (set-style-foreground red-style "red")

  Then, define a short command 'goto-style' like so:

    (defun goto-style (newstyle)
      "Set current buffer to a given font NEWSTYLE."
      (setq buffer-style newstyle)
      (redraw-display))

  Next, bind commands to keys like so:

    (global-set-key "\C-c1" (definteractive (goto-style red-style)))

  This binds a command that changes the current foreground color to red
  to the key sequence C-c 1.

  The following function allows you to interactive specify a new color
  for the current buffer's foreground:

    (defun set-foreground (newfg)
      "Set current foreground color to NEWFG."
      (interactive "sForeground color: ")
      (set-style-foreground buffer-style newfg)
      (redraw-display))

  This function is activated by typing:

    M-x set-foreground

  Or, it can be bound to a key like so:

    (global-set-key "\C-z\C-s" 'set-foreground)

D-2: How do I switch fonts interactively?

  To change fonts, you don't have to define new styles.  Just define a
  short command 'goto-font', like so:

    (defun goto-font (newfont)
      "Set current buffer to a given font NEWFONT."
      (font newfont)
      (redraw-display))

  Then, bind commands to keys like so:

    (global-set-key "\C-c1" (definteractive (goto-font "8x13")))

  This changes the current edit window's font to "8x13" when the key
  sequence 'C-c 1' is entered.

  The following function allows you to interactively input a font name:

    (defun set-font (newfont)
      "Set current font to NEWFONT."
      (interactive "sFont name: ")
      (font newfont)
      (redraw-display))

  This function is activated by typing:

    M-x set-font

  Or, it can be bound to a key like so:

    (global-set-key "\C-z\C-s" 'set-font)

  If the font you specify with either of these methods isn't valid for
  your X server (i.e. if the font doesn't exist in a directory listed in
  your X server's font path and in that directory's fonts.dir file, or
  isn't available from the font server if you're running X11R5), you
  will get this message in your minibuffer:

  Bad font name

  Font names are ordinary X font names; for example, a 14-point non-bold
  non-italic Helvetica font can be referred to as:

  "*helvetica-medium-r-normal--14*"

  The standard X client 'xlsfonts' will give you a list of the fonts
  registered with your X server.  The standard X client 'xfontsel' lets
  you interactively put together an X font specification string based on
  individual attributes (e.g., family, size).

D-3: How can I associate a certain foreground color with a file
 so that every time I load that file my foreground color is
 automatically set?

  You can easily do this by using GNU Emacs' ability to handle file
  variables.  For example, if you have defined style 'red-style' to
  specify a red foreground color, and want file 'foobar.c' to always
  have the foreground color red, add this to the bottom of 'foobar.c':

    ^L
    /*
    Local Variables:
    buffer-style: red-style
    End:
    */

  NOTE: '^L' is a newline character; you can enter one in an edit
  buffer by typing 'C-q C-l'.

  Then, whenever 'foobar.c' is loaded, the variable 'buffer-style' will
  be set to 'red-style', and as a result the foreground color for that
  buffer will be red.

D-4: How do I design my own really funky technicolor modeline?

  Using the tried-and-true Learning By Example(tm) educational method,
  I'll just give the (heavily commented) elisp code I use to define my
  own customized modeline:

  ;; A style to emphasize things I find important
  (defvar mode:*hilight-style*  (make-style)
    "Style for modeline hilights"
  )
  (let ((s1 mode:*hilight-style*))
   ;; Do something reasonable if we're on a monochrome screen
    (if (> (epoch::number-of-colors) 2)
        (progn
      (set-style-foreground s1 "#83558c")
      (set-style-background s1 (foreground)))
      (progn
      (set-style-foreground s1 (background))
      (set-style-background s1 (foreground))))
    (set-style-font s1 "*helvetica-bold-r-*-*-12-*")
  )

  ;; A style for normal modeline contents -- inverted from normal
  ;;  buffer
  (defvar mode:*normal-style* (make-style)
    "Normal modeline style"
  )
  (let ((s2 mode:*normal-style*))
    (set-style-foreground s2 (background))
    (set-style-background s2 (foreground))
    (set-style-font s2 "*helvetica-medium-r-*-*-12*")
  )

  ;; define  a simpler-looking modeline format
  (setq default-mode-line-format
    (list
      ""
      'mode:*normal-style*
      'mode-line-modified
      ;; Highlight the buffer name
      'mode:*hilight-style*
      " %17b"
      'mode:*normal-style*
      "   "
      'global-mode-string
      "   %[("
      'mode-name 'minor-mode-alist "%n" 'mode-line-process
      ")%]--"
      ;; Highlight where we are in the buffer
      'mode:*hilight-style*
      (cons -3 "%p")
      'mode:*normal-style*
      "-%-"
      )
    )


D-5: How do I replace the mouse region selection underlining with a
 different style?

  The appearance of the region underlined with the mouse is described
  by the style in the variable "motion::style".  You can use the
  normal style functions to manipulate this variable.  For example,
  you can turn off underlining with the following:

    (set-style-underline motion::style nil)

  Now, nothing will show up.  To have just the text foreground color
  change on mouse selection, do:

    (set-style-foreground motion::style "yellow")
    (set-style-background motion::style (background))

  Replace "yellow" with any desired X color name.

  To have the selected region appear as reverse video, try:

    (set-style-foreground motion::style (background))
    (set-style-background motion::style (foreground))

  To have the selected region appear with an overlayed diagonal stipple
  pattern, try:

    (set-style-background motion::style "red")
    (set-style-background-stipple motion::style
      (make-bitmap 4 4 "\167\273\335\356"))

  The style bound to motion::style has default settings as follows:

    (set-style-foreground motion::style (foreground))
    (set-style-background motion::style (background))
    (set-style-underline motion::style (foreground))

*                           === MENUS ===

E-1: Does Epoch support popup menus or menubars?

  The base Epoch distribution does not have native support for popup
  menus or menubars.  However, there are other ways to use menus with
  Epoch.

  METHOD #1:

  If you're running the window manager GWM (available via anonymous
  FTP to export.lcs.mit.edu (18.24.0.12) in /contrib/gwm), you can use
  the Epoch contrib 'wm-menu' package (found in the contrib tar file
  on cs.uiuc.edu) to have GWM provide menus that pass messages to
  Epoch.

  METHOD #2:

  If you're running a window manager that has user-specifiable menus
  (as all of the common window managers do), you can perform
  particular commands from a menu.  These commands can communicate
  with epoch, and get it to do things.

  One way to do this is to use "xse" (XSendEvent) and send characters
  that happen to be bound to the commands you want to activate.  To
  bind arbitrary commands to menu entries in this manner, you need to
  define a unique keystroke pattern (with global-set-key) for each
  command and then send that keystroke pattern with xsendevent via the
  menu.  See the section on rebind-key (below) for more information on
  this technique.  (Of course, you are also free to have xsendevent
  send a key sequence like 'ESC x u n d o RET' directly to Epoch.)

  A better way is to use gnudoit, which communicates to gnuserv.
  Gnuserv, gnuclient, and gnudoit are replacements for emacsclient and
  its server.  With gnudoit, you can pass in an Emacs Lisp form to
  evaluate, rather than the less readable X Event description for a
  key binding.

  Some window managers (such as TWM) do not allow the user to specify
  client-specific menus -- you can only add menus to all clients.
  This is not an ideal solution, since all windows (Epoch or not) in
  the session will have the menu attached to them, but it does work
  and is quite convenient for use with Epoch.  Other window managers
  (Mwm in particular) allow you to specify a menu on a
  client-by-client basis.  Thus, you can have different menus on
  terminal windows from on Epoch (Mwm will even let you have different
  menus on different screens and on the minibuffer).

  Here's a couple of sample Twm menu descriptions.  Note that these
  would show up on all applications that have title bars.

  menu "epoch"
  {
    "Epoch Menu"   f.title
    "Undo"         ! "xse 'Ctrl<Key>x' '<Key>u'"
    "Quit"         ! "xse 'Ctrl<Key>x' 'Ctrl<Key>c'"
  }
  LeftTitleButton "~/epochbitmap.bm" = f.menu "epoch"

  Or, using gnudoit (notice the more readable function names):

  menu "epoch"
  {
    "Epoch Menu"   f.title
    "Undo"         ! "gnudoit '(undo)'"
    "Quit"         ! "gnudoit '(save-buffers-kill-emacs)'"
  }
  LeftTitleButton "~/epochbitmap.bm" = f.menu "epoch"


  Here's an equivalent Mwm menu, along with resources that will place
  the menu only on Epoch windows.

  This goes in your Mwm config file:
  Menu EpochMenu
  {
      "Epoch" f.title
      "Undo"  ! "gnudoit '(undo)'"
      "Quit"  ! "gnudoit '(save-buffers-kill-emacs)'"
  }

  This goes in your X defaults:
  Mwm*epoch*windowMenu: EpochMenu

  Note the "*epoch*" -- this is the class name of the screen.  If you
  use the -name or -rn options (as described in A-6), this name will
  change.  See the "class" attribute of screens in the epoch manual
  for more on this.

  You can get xsendevent at export.lcs.mit.edu (18.24.0.12) in /contrib
  or at ftp.uu.net (137.39.1.9) in /packages/X/contrib.  Gnuserv,
  gnuclient and gnudoit are available at ee.utah.edu, in
  /emacs/etc/gnuserv (and probably other sites, too, but I can't find
  any with Xarchie -- anyone got a good one?).

  [From Philippe Bondono ([e-mail])., with Mwm and
  gnuclient additions by Brook]

  METHOD #3:

  A completely different technique involves using a separate X client
  that posts a menu and has Epoch (or for that matter, GNU Emacs)
  receive commands from it.  One example of this technique is
  /gnu/emacs/buttons.tar.Z from anonymous FTP to aix370.rrz.uni-koeln.de
  (134.95.132.2).

  METHOD #4:

  Another method uses xmenu or xmenu2, which are available at any
  comp.sources.x archive.  (If you don't know of such an archive, try
  anonymous FTP to ftp.uu.net (137.39.1.9) in /usenet/comp.sources.x.)
  After you have compiled xmenu or xmenu2, define the following function
  in your .emacs file:

  (defun interpret-output (process output)
    (command-execute (car (read-from-string output))))

  Then you can define other functions that make specific menus, with
  menu entries bound to commands, like the following example shows:

  (defun make-menu ()
    (interactive)
    (set-process-filter (start-process "xmenu" nil
        "/usr/local/bin/xmenu" "-heading" "Epoch Menu"
        "Undo=undo")
      'interpret-output))

  This example uses /usr/local/bin/xmenu to post a one-entry menu to the
  screen; the menu entry's label is "Undo" and the action it triggers in
  Epoch is 'undo'.  Specify as many "Label=action" pairs as you like as
  part of the start-process command.

  [From Philippe Bondono ([e-mail]).]

  If you use XView/Open Windows, Dev Joneja ([e-mail])
  has written a menu/button client similar to xmenu; it's available via
  anonymous FTP from ftp.ncsa.uiuc.edu (141.142.20.50) as
  /outgoing/marca/epoch/xvmenu.tar.Z.

  Bob Weiner ([e-mail]) says the following concerning menus
  within Hyperbole:

  ----------------------------------------------------------------------
  If you use Hyperbole, you know what the Smart Key system is, context
  sensitive key bindings for many Emacs modes and subsystems.  There is
  a Smart Menu system that goes along with this but has not been
  released because it needs some additional menus and some integration
  work.  It is window manager and window system independent, works under
  Emacs, with a slightly customized version that can highlight selected
  menu items and display menus in a separate Epoch screen, and is
  written entirely in Elisp, so no patching is needed.  It provides much
  easier subsystem access for novices and experienced users and has been
  in use at a few sites for the last several years.

  I'd like to get it in a form for release but won't have the time for
  several months.  If an experienced Elisp programmer wanted to
  integrate it with Hyperbole and make any other changes, I [Bob, not
  Marc] would be willing to send it out and coordinate on and test the
  final changes.
  ----------------------------------------------------------------------

  See the list of FTP sites below for more information on Hyperbole.

*                          === KEYBOARD ===

F-1: How do I make the backspace key work properly?

  This is actually a GNU Emacs question, but it's included in this FAQ
  because it's probably more important to more people than all the
  other questions here.  (One of the great mysteries of GNU Emacs is
  why the backspace key _still_ doesn't do its job.)

  Here are four ways to fix this:

  METHOD #1:

  Put this in your .emacs file:

    (rebind-key "BackSpace" nil "\C-?")

  This is the cleanest Epoch-specific solution.  It rebinds
  the X representation for the backspace key directly to that
  of the delete key.

  [Thanks to Joe Wells ([e-mail]).]

  METHOD #2:

  Put this in your .emacs file:

    (global-set-key "\C-^bdc" 'backward-delete-char-untabify)
    (rebind-key "BackSpace" nil "\C-^bdc")

  This rebinds the X representation for the backspace key to the
  appropriate command for deleting a character backward.  Like the
  first method, this is Epoch-specific.

  If you don't like to have your backspace key also untabify (i.e.,
  convert tags to spaces on the fly), use this instead of the previous
  global-set-key:

    (global-set-key "\C-^bdc" 'backward-delete-char)

  METHOD #3:

  Put this in your .emacs file:

    (global-set-key "\C-h" 'backward-delete-char-untabify)
    (global-set-key "\C-xh" 'help-command) ; override mark-whole-buffer

  This makes C-h (the backspace key as well as the Control-h key
  sequence) delete characters backward, and shifts responsibility for
  help to C-x h.  This fix will work for GNU Emacs as well as Epoch.

  If you don't like to have your backspace key also untabify (i.e.,
  convert tabs to spaces on the fly), use this instead of the previous
  global-set-key for C-h:

    (global-set-key "\C-h" 'backward-delete-char)

  METHOD #4:

  Outside of Epoch, you can change the X representation of the
  BackSpace key into a Delete by doing this:

    xmodmap -e "keysym BackSpace = Delete"

  This approach has the disadvantage of not being done inside
  of Epoch for those who prefer customizing lisp code to
  customizing their system environments.

  [Thanks to Joe Wells ([e-mail]).]

F-2: How do I make the keys marked "Page Up" and "Page Down" on an IBM
 Selectric-style keyboard do their jobs?

  Using the key rebinding facility discussed below, you can put the
  following two lines in your .emacs file:

    (rebind-key "Prior" nil "\M-v") ; Note Prior, not Page Up.
    (rebind-key "Next" nil "\C-v")  ; Note Next, not Page Down.

  Similarly, if you want "Home" and "End" to go to the beginning and end
  of the current buffer respectively, do:

    (rebind-key "Home" nil "\M-<")
    (rebind-key "End" nil "\M->")

F-3: How do I bind keys in the numeric keypad on an IBM Selectric-style
 keyboard to their obvious functions (arrow movement, home, end, etc.)?

  Put these lines in your .emacs file:

    (rebind-key "KP_Home" nil "\M-<")
    (rebind-key "KP_Up" nil "\C-p")
    (rebind-key "KP_Prior" nil "\M-v")
    (rebind-key "KP_Left" nil "\C-b")
    (rebind-key "KP_Begin" nil "\C-l")
    (rebind-key "KP_Right" nil "\C-f")
    (rebind-key "KP_End" nil "\M->")
    (rebind-key "KP_Down" nil "\C-n")
    (rebind-key "KP_Next" nil "\C-v")

  NOTE: This makes the keypad arrow keys work, the keypad PgUp/PgDown
  work, and the keypad Home/End go to the beginning/end of the
  buffer.

  Other keys appropriate for rebinding in a Selectric-style numeric
  keypad include KP_Divide, KP_Multiply, KP_Subtract, KP_Add, KP_Enter,
  KP_Insert, and KP_Delete; see below for more details.

F-4: What general facilities does Epoch provide for rebinding function
 keys, and how do I use them?

  The rebind-key function allows you to rebind any keycode to a new
  string.  An example is probably best to show how this works.  To make
  the key marked "Page Up" (on IBM Selectric-style keyboards) actually
  move the current buffer up a page (like M-v), do:

    (rebind-key "Prior" nil "\M-v")

  Note that "Prior" is the actual X keysym name for the "Page Up" key;
  to see the X keysym names, refer to /usr/include/X11/keysymdef.h (or
  $OPENWINHOME/include/X11/keysymdef.h on OpenWindows systems).
  (Disregard the leading XK_ in keysymdef.h's definitions for Epoch's
  purposes; thus, X11's "XK_Prior" becomes Epoch's "Prior".  To find out
  which keys are actually active for your keyboard and server, use the
  command "xmodmap -pk".)

  The standard function keys are named F1 through F12, the function keys
  on the left side of a Sun-style keyboard are named L1 through L10, and
  so on.  The keypad apparently cannot be addressed by KP_0 through KP_9
  but must be referenced by names like KP_Left, KP_Up, and so on.

  A simple two-step approach for binding function keys to commands
  involves binding a key to an arbitrary GNU Emacs key encoding (in the
  following example, C-^ k 1) and then binding that encoding to the
  command.  An example that binds the function key marked "End" to an
  arbitrary command (in this case, end-of-line) follows:

    (rebind-key "End" 0 "\C-^k1")
    (global-set-key "\C-^k1" 'end-of-line)

  Note that the above is only an example of the two-step method; if you
  really want "End" to do 'end-of-line, do the obvious instead:

    (rebind-key "End" 0 "\C-e")

  The rebind-key command allows modifiers (e.g. shift, control) to be
  specified; the following example binds Control-"End" to an arbitrary
  command (in this case, end-of-buffer):

    (rebind-key "End" 'control "\C-^Ck1")
    (global-set-key "\C-^Ck1" 'end-of-buffer)

  For an example of these principles in action, see the file
  'amc/keys.el' in the 3.2 contrib directory (which is still up for
  anonymous ftp at cs.uiuc.edu as a separate .tar.Z file) or at
  ftp.ncsa.uiuc.edu in /outgoing/marca/epoch.

  [Thanks to Alan Carroll ([e-mail]).]

F-5: I want Epoch to disregard accidental presses of function keys that
 insert spurious characters (e.g., "-1~") into the buffer.  Does Epoch
 perchance have some magical way to make this happen?

  Perchance, Epoch does.  The variable epoch::function-key-mapping, if
  set to nil, makes Epoch disregard such keys, unless they're explicitly
  rebound with rebind-key.  You can set this in your .emacs file like
  so:

    (setq epoch::function-key-mapping nil)

  [Thanks to Alan Carroll ([e-mail]).]

F-6: How do I turn the keyboard bell off?

  The easy answer is to put the following line in your .emacs file:

    (setq epoch::bell-volume -50)

  Another possibility, if you like visual bells (i.e., having the
  entire edit window flash reverse video instead of hearing an audible
  beep), is to put the following in your .emacs file:

    (epoch::set-bell t)

  The malicious answer, for those who, like myself, never want to hear
  another beep for the rest of time, is to modify src/x11term.c in the
  Epoch distribution; just change the line that reads:

    XBell (xs->display,volume);

  To:

    /* XBell (xs->display,volume); */

  Then recompile.

*                        === HIGHLIGHTING ===

G-1: How do I highlight regions of text in a buffer with different styles?

  While the current Epoch distribution contain plenty of support for
  zones and styles, the enabling mechanisms that make syntax-directed
  highlighting possible, no intrinsic support for such highlighting is
  provided.  This situation may change in subsequent releases of Epoch.

  Three packages that provide varying degrees of support for
  syntax-directed highlighting are:

  tek-highlight-2.0.tar.Z (available from archive.cis.ohio-state.edu
  or ftp.ncsa.uiuc.edu, see below), which supports comment highlighting
  in source code as well as support for the Info documentation browser,
  various mail and news packages, and manual pages.

  lightbrite.tar.Z (available from ftp.ncsa.uiuc.edu, see below),
  written by Marc Andreessen to allow per-mode regexp-based
  highlighting.  Thus, you can have all #define's/#endif's in red,
  setq's and defun's in green, int/float/double's in yellow, '-->'s in
  purple, and so on.  Here's something from its README:
   o Accurate comment highlighting.
   o Regexp touchup highlighting.
   o Easy specification of visual attributes of multiple
      highlighting styles.
   o Instant highlighting (as you type) with adjustable
      responsiveness.
   o Buffer size thresholds for both comment and touchup
      highlighting.
   o Use of minor mode and local keymaps.
   o Re-highlight visible screen, current paragraph, current
      function, immediate area, or entire buffer.
   o Large assortment of default mode-specific highlighting
      patterns.
   o Automatic highlight on find-file and/or write-file.
   o Special handling of mail and rmail modes.
   o Works with both Epoch and Lucid Emacs transparently.

  hilit.el.Z (most recent version was posted to gnu.emacs.souces and is
  available from ftp.ncsa.uiuc.edu, see below), which provides
  source-code comment and regexp highlighting.

*               === EPOCH-SPECIFIC ELISP PACKAGES ===

H-1: Where can I find Epoch-specific elisp packages?

  Try the following anonymous FTP sites for Epoch-specific elisp
  packages:

  aix370.rrz.uni-koeln.de (134.95.132.2)
    /gnu/emacs

  archive.cis.ohio-state.edu (128.146.8.52)
    /pub/gnu/emacs/elisp-archive/elisp
    [This is main elisp-archive site; it is mirrored at
     ftp.uu.net (137.39.1.9) in /languages/emacs-lisp, among other places.
     Not much Epoch code exists here; in particular, a much more
     recent version of hilit.el.Z is at ftp.ncsa.uiuc.edu, below.]

  ftp.cs.buffalo.edu (128.205.32.3)
    /pub
    [This is the distribution site for the new Dired, which will
     be included in Emacs v19; it includes support for Epoch.]

  ftp.ncsa.uiuc.edu (141.142.20.50)
    /outgoing/marca/epoch
    [This is the previous FAQ maintainer's archive of Epoch code; the
     README file gives an overview of what he considers to be
     'essential' Epoch packages, and all of those packages
     are available there.  If he gets out of date on any of
     these and you notice it, please let him know.]

  icsi-ftp.berkeley.edu (128.32.201.55)
    /pub/elisp

  ireq-robot.hydro.qc.ca (131.195.2.130)
    /pub/emacs/lisp
    [This is the distribution site for the IMOUSE package.]

  wilma.cs.brown.edu (128.148.31.66)
    /pub/hyperbole
    [This is the distribution site for the Hyperbole hypertext
     system, which includes support for Epoch.  Also available
     separately from here is the wrolo 'rolodex' package, one of the
     components of Hyperbole.]

  Also see the contrib tar file found at cs.uiuc.edu, in the same
  directory as the actual Epoch distribution.

  Also watch the gnu.emacs.sources Usenet newsgroup, as well as the
  epoch newsgroup/mailing list (see below).

  Please volunteer the names of any sites not on this list.

H-2: Where can I get a PostScript version of the Epoch manual?

  Use anonymous ftp to cs.uiuc.edu (128.174.252.1) in
  /pub/epoch-files/epoch; get epoch-4.0.epoch-man.ps.Z.

*                      === OTHER RESOURCES ===

I-1: What Epoch newsgroups/mailing lists are out there?

  The Usenet newsgroup gnu.epoch.misc and the mailing list
  [e-mail] are one and the same.  To join the mailing list,
  send a request to [e-mail].  (It is best to read the
  newsgroup if you have access to it, to save on network resources and
  the mailing list maintainer's time.)

  For more general information about Epoch and GNU Emacs, see the list
  of resources at the start of this file.

I-2: Where do I send bug reports?

  Either post to the newsgroup gnu.epoch.misc, or (equivalently) send
  mail to [e-mail] (which is the newsgroup).

*                     === ADVANCED QUESTIONS ===

  [NOTE: This section is at the bottom since the questions involve
  actual source-code hacking or problems with specific machine
  configurations that the FAQ moderator cannot personally verify and
  whose solutions will probably involve some sort of hacking.  If
  these answers helped you, please let me know.  If I don't hear of
  people finding these useful, I'm going to remove them.]

Z-1: Epoch 4.0b1 (or later) (as well as GNU Emacs 18.58) built under
 HP-UX 8.0 and 8.05 apparently don't recognize the Meta key as Alt.
 How can this be fixed?

  Bob Fisher ([e-mail]) suggests the following command,
  executed once per session, prior to starting Epoch:

          xmodmap -e "clear mod1"        \
                  -e "add mod1 = Meta_R" \
                  -e "add mod1 = Meta_L"

Z-2: Why do all of Epoch's colors go away when Epoch is run on an X11R5
 server with multiple screens?

  Dana Chee ([e-mail]) reports that X11R5 has a new
  SCREEN_RESOURCES property that allows/forces colors to only appear for
  color screens, but Epoch doesn't look at this property.  This bug
  will only bite you if you're running on a multi-screen system.  If it
  happens, there is a workaround; see the xrdb manpage and the xrdb
  option '-all'.

Z-3: Even though Epoch 4.0b1 includes fixes to keep the cursor from
 disappearing (as it does on occasion, especially in a shell, in
 Epoch 4.0b0), the cursor still disappears sometimes.  Is there a fix
 for this?

  First, Epoch 4.0p0 has additional fixes for this problem which
  presumably will supersede the fix given below.

  According to Michael Thome ([e-mail]), activating the XFlush
  code at the end of the CursorToggle routine in 4.0b1's x11term.c seems
  to fix the problem.  (In other words, '#if 0' on line 737 of x11term.c
  should be changed to '#if 1'.)

Z-4: I want Epoch to iconify itself immediately upon starting.  To this
 end, in my .emacs file I have (epoch::iconify-screen).  But most
 (~95%) of the time this doesn't work.  How can I make it work all the
 time?